Updating the Tor binary included with Ricochet #618
Conversation
|
Preview: http://62.102.148.154:19472/#im |
|
@beardog108 Thoughts? |
ghost
requested a review
from
|
@tya99 I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning), because it takes up too much screen real estate just for people who want to use ricochet |
There was a problem hiding this comment.
@tya99 I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning), because it takes up too much screen real estate just for people who want to use ricochet
I agree. Did you write this yourself @tya99? If not, please link to the original content instead.
Could do that however I think that might detract from how important it is. Perhaps we could put it at the end after "Related Information". Ideally it would be great if we had foldable headings on the privacytools.io page like this for example.
Yes I did. See Issue #474 part of the reason I am reluctant to just leave it as a github comment. Should something happen to github or the repository or even the privacytoolsIO account it would be lost and not tracked within source control. |
|
Books often have sections with info like this at the end. Maybe we could create a separate page for these things? |
|
@Shifterovich If we still have a link that would jump/go to the section, that would be acceptable. |
|
If we move this section to the bottom of the page, the links will work. |
|
This depends on https://github.com/privacytoolsIO/privacytools.io/issues/746 |
ghost
mentioned this pull request
|
We'll figure something out soon. |
|
Done. Thanks @tya99 |
Description
Screenshot:
Resolves: #474